Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[fix]: fixed edge case crash cases if notifications are processed nearly simultaneously #2946

Merged
merged 2 commits into from
Oct 21, 2024

Conversation

foxriver76
Copy link
Collaborator

@foxriver76 foxriver76 commented Oct 21, 2024

Link the issue which is closed by this PR

Implementation details

In #2944 a controller crash occured if notifications were cleaned nearly simultaneously, and we only checked that the index is present at the beginning of the file and not re-checked after doing asynchronous operation. Hence, we added noUncheckedIndexedAccess for the tsconfig (only common package) to avoid these cases.

Tests

  • I have added tests to avoid a recursion of this bug
  • It is not possible to test for this bug

If no tests added, please specify why it was not possible

Not really possible, but we avoided these cases by adapting the tsconfig for adding noUncheckedIndexedAccess rule for this file.

…ultaneously

- closes #2944
- added more strict tsconfig to allow migrating single files to stricter rules
@foxriver76 foxriver76 merged commit ecac4b4 into master Oct 21, 2024
12 checks passed
@foxriver76 foxriver76 deleted the issue-2944 branch October 21, 2024 09:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[bug]: v7 Cannot convert undefined or null to object
2 participants